Firewall interface configuration and processes to enable bi-directional VoIP traversal communications

ABSTRACT

A firewall configured to be interfaced between an internal and an external networks. The firewall includes a VoIP processor for detecting an outgoing VoIP packet sent from the internal network, for changing data in a header of the VoIP packet and also changing data contents in the VoIP packet corresponding to data changed in the header to enable bi-directional VoIP communication. In one embodiment, the VoIP processor changes a source IP address and a port number in the header of the VoIP packet and also changes the data contents in the VoIP packet corresponding to the source IP address and the port number changed in the header to enable bi-directional VoIP communication. In another embodiment, the firewall further includes an external VoIP interface comprising multiple VoIP ports for receiving multiple incoming VoIP packets each designated with one of the VoIP ports. And, the VoIP processor further includes a VoIP port versus internal address table for identifying an internal address in the internal network for directing each of the incoming VoIP packets to the internal address identified.

BACKGROUND OF THE INVENTION

1. Field of the Invention

Embodiments of the present invention generally relate to the managementand processes of the network communication packet implemented with afirewall. More particularly, this embodiments of the present inventionrelate to a new interface configuration and processing scheme forenhancing bi-directional VoIP communication traversing the firewallwithout degrading the level of protections provided by the firewall.

2. Descriptions of the Reference Art

A technical difficulty is still faced by those who apply InternetProtocol (IP) for voice communication by sending voice messages asdigitized data packets on Internet, commonly known as Voice over IP(VoIP) technologies, when the sender or the receiver are protected by afirewall protection system. Specifically, several popular VoIP signalingprotocols such as MGCP, SIP and H323 are commonly implemented. All thesedifferent types of protocols are implemented with the data relating tothe end point address embedded as part of the data content transmittedin the Internet Protocol packets. Referring to FIG. 1 for a typicalfirewall setup where the firewall is installed as a protection interfacebetween the internal and external networks for preventing invasions ofundesirable transmission between the internal and external networks. Aconventional firewall employs a network address translation (NAT)technique to change the IP packet header such that all outgoing packetsfrom the internal network are presented to the external network as ifthere are sent out from the firewall. However, once the sender'sidentification, i.e., the source IP address and port number of thesender, is translated and changed by the firewall, a return packet inresponse to the sender's VoIP packets can only return to the firewalland would be unable to reach the sender. The communication loop isbroken due to the operation of the firewall in changing the source IPand the source port numbers. For a packet sent from the internal networkto the external network through the firewall, it would typically includethe header information of source IP address, protocol type, source portnumber, destination IP address and destination port number. An exemplaryheader is shown below:

-   Source IP: 192.168.100.1-   Protocol: UDP-   Source port: 1025-   Destination IP: 10.1.2.3-   Destination port: 2727    After the packet is processed by the firewall, the header data is    changed and an example of the changed header is shown below:-   Source IP: firewall's external IP address-   Protocol: UDP-   Source port: allocated by the firewall (for example 3330)-   Destination IP: 10.1.2.3-   Destination port: 2727

For the security of the network user protected by the firewall, theSender's IP address is therefore changed and hidden from the externalnetwork. It is noticed that the destination IP and port number are notchanged. The same IP address and port number maybe included in thecontent of the IP packets too. Specifically, a valid SIP request mustcontain the following header fields: To, From, CSeq, Call-ID,Max-Forwards, and Via; all of these header fields are mandatory in allSIP requests. Call-ID in this case includes a port number and IP address(or domain name) of an end point. For the outbound traffic, i.e., IPpackets transmitted from the internal private network to an externalpublic network, because the conventional firewall only changes thepacket header, the end point address embedded in the packet contentstill points to the original IP addresses and the embedded IP addresswill be mismatched with the header now changed by the firewall. Due tothe mismatches, the VoIP communication cannot be successful.Furthermore, for the inbound VoIP communications, because the internalhost's IP addressees are hidden from the public network, VoIP trafficwhen designate the IP address and the port number of an internal IPaddress cannot reach individual end point by their IP address, thus anincoming call cannot be made. Additionally, even a special assignment ismade to correlate a port number with an end point of an internal user,since for each specific protocol, the port number is fixed, for exampleport 2427 is for MGCP, and 2543 is for SIP. So in a conventionalfirewall for the management of incoming traffic, if a packet istargeting port 2427, it usually is a call. However, since only one portis used, a call can only be made to one end point inside firewall usingthe conventional method.

In summary, VoIP is a major enabler of high-value, converged voice/dataapplications. However, widespread use of VoIP is at odds withconventional security technology: Network-level devices, such as NATgateways, lack the intelligence to recognize and properly process thecritical signaling protocols that enable VoIP calls to be establishedand managed. Until now, extreme compromises have been required to enableflexible VoIP applications: Companies have been forced to eithercompromise their security, by opening holes in their perimeter securityto allow VoIP signaling to pass, or have been forced to purchaseexpensive, single-function call-proxy systems that focus on solving theNAT traversal problem. Another approach—using VoIP only in conjunctionwith VPN tunnels—greatly limits the reach of Internet telephony. None ofthese so-called solutions achieves the goal of enabling widespread,secure use of VoIP technology.

Since there is an increase in adopting voice over IP technology in theenterprise environment spawning from renewed interest in convergedvoice/data application, there is an urgent need to resolve thedifficulties. Particularly, as most conventional network securitytechnologies employ the network address translation (NAT) technique as auniversal standard to prevent unauthorized access to a private networkfrom the Internet, these difficulties often force organizations toeither comprise security or forsake the voice/data convergence becausesuch applications have become impractical.

Therefore, a need still exits in the art to provide improved firewallsystems with more intelligent operations capable of managing both VoIPand non-VoIP network communications in order to resolve thesedifficulties.

SUMMARY

According to one embodiment of the present invention, a new and improvedinterface configuration and processing scheme for a network protectiongateway (NPG) are provided to manage packet transmission. The networkprotection gateway provides both network layer and application layerprotection, and through their content-aware proxy architecture,understand and parse VoIP packets at the application layer, therebysolving, the VoIP NAT traversal problem. The NPGs as disclosed accordingto various embodiments of the present invention maintain high levelsecurity while enabling VoIP call setup and call transmission at veryhigh performance. The technologies as disclosed in accordance withembodiments of the present invention are useful to support all kinds ofVoIP signaling protocols.

In one embodiment of the present invention, a firewall for interfacingbetween an internal and an external networks includes a VoIP processingmeans for detecting an outgoing VoIP packet sent from the internalnetwork for changing data in a header of the VoIP packet and alsochanging data contents in the VoIP packet corresponding to data changedin the header to enable a bi-directional VoIP communication. In oneembodiment, the VoIP processing means changes a source IP address and aport number in the header of the VoIP packet and also changes the datacontents in the VoIP packet corresponding to the source IP address andthe port number changed in the header to enable a bi-directional VoIPcommunication. In another embodiment, the firewall further includes anexternal VoIP interface comprising a plurality of VoIP ports forreceiving multiple incoming VoIP packets each designated with one of theVoIP ports. And, the VoIP process means further comprising a VoIP portversus internal address table for identifying an internal address in theinternal network for directing each of the incoming VoIP packets to theinternal address identified.

Various embodiments of the present invention also disclose methods fortransmitting a VoIP packet from an internal network through a firewallto an external network. According to one embodiment, the method includesa step of detecting an outgoing VoIP packet sent from the internalnetwork for changing data in a header of the VoIP packet and alsochanging data contents in the VoIP packet corresponding to data changedin the header to enable a bi-directional IP VoIP communication. In apreferred embodiment, the step of changing the data in the header of theVoIP packet comprising a step of changing a source IP address and a portnumber in the header of the VoIP packet and the step of changing thedata contents in the VoIP packet further comprising a step of changingthe data contents in the VoIP packet corresponding to the source IPaddress and the port number changed in the header to enable abi-directional VoIP communication. In another preferred embodiment, themethod further includes a step of providing a plurality of VoIP ports toan external VoIP interface for receiving multiple incoming VoIP packetseach designated with one of the VoIP ports. And, identifying an internaladdress in the internal network corresponding to the VoIP portdesignated in each of the incoming VoIP packets for directing each ofthe incoming VoIP packets to the internal address identified.

These and other objects and advantages of the present invention will nodoubt become obvious to those of ordinary skill in the art after havingread the following detailed descriptions of the preferred embodimentthat is illustrated in the various drawing figures.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a system configuration of a network system includinga firewall installed between an internal and external networks forprotecting and controlling the interfaces between the internal andexternal networks;

FIG. 2 is a flow chart showing the processing steps carried out by afirewall to provide corrected end point IP addresses and port numberssent out by the firewall according to an embodiment of the presentinvention;

FIG. 3 illustrates a system configuration of a firewall that includes aninterface opened with multiple ports for receiving multiple incomingVoIP calls according to an embodiment of the present invention;

FIG. 4 is a flow chart showing the processing steps carried out by afirewall to direct multiple incoming VoIP calls to end points withcorrect internal IP addresses and port numbers; and

FIGS. 5A to 5K are screen display illustrations and IP address tablesfor showing the processes according to an embodiment of the presentinvention.

DETAILED DESCRIPTION

Reference will now be made in detail to the various embodiments of thepresent invention. It will be understood that the disclosure is notintended to limit the invention to any particular embodiments. On thecontrary, the invention is intended to cover alternatives, modificationsand equivalents, which may be included within the spirit and scope ofthe disclosure and the attached claims. As will be appreciated by one ofskill in the art, the present invention may be embodied as a method,data processing system or computer software program products.Accordingly, the present invention may take the form of data analysissystems, methods, analysis software and etc. Software written accordingto the present invention may be stored in some form of computer readablemedium, such as memory, or hard-drive, CD-ROM. The software may betransmitted over a network and executed by a processor in a remotelocation. The software may also be embedded in the computer readablemedium of hardware, such as a network gateway device or a network card.

Referring to FIG. 2, a flowchart will now be described to illustrate theprocessing steps carried out by a new firewall processor according toone embodiment of the present invention. According to embodiments of thepresent invention, bi-directional VoIP protocol traversal communicationis facilitated without compromising security. According to the presentexample, the process begins (step 100) when a VoIP user of an internalnetwork system protected by a firewall sends out VoIP packets (step 105)for VoIP communication. The firewall receives the IP packets and changesthe source IP address and the source port number in the packet header toan external IP address as if the packets have been originated by thefirewall (step 110) and changes the port number to a port numberdesignated by the firewall (step 115). The firewall then checks whetherthe IP packets are VoIP packets (step 120). If the packets aredetermined to be VoIP packets, then the firewall also changes the endpoint addresses and port numbers embedded in the packets to the new IPaddress, e.g., the external firewall IP address and the new port number,i.e., the new port number as designated by the firewall, to identify thesender of the message as an internal network user (step 125). After theembedded end point address and port number are changed, the VoIP packetsare sent out (step 130) and the processes end (step 135). The end pointIP address and the port number in the VoIP requests embedded in the IPpackets are now consistent with the header of the IP packets. In thismanner, the firewall provides correct IP address and port designationsfor a VoIP message receiver to respond to the message sender. The VoIPmessage receiver responds to the message sender by sending theresponsive VoIP packets to the firewall according to the port numberdesignated by the firewall. The difficulty described above is thereforeresolved by allowing a message sender protected by a firewall tocommunicate with a message receiver with correct and consistent endpoint address information without being affected by the Network AddressTranslation (NAT) operation of the firewall.

In order to receive the inbound VoIP network communications, embodimentsof the present invention provide new and improved firewallconfigurations to enable the recognition of the internal host's IPaddresses that are hidden from the public network. Referring to FIG. 3,a block diagram of a firewall will now be described according to oneembodiment of the present invention. As shown in the example of FIG. 3,the firewall may provide many ports on its external interface(s). Eachport/IP pair corresponds to one end point in the internal network. Therelationship of port/IP pair and endpoint address can be advertisedautomatically to a third computer on the network through a directorysystem, or it can be manually input into both the firewall and theexternal call manager. Thus, when the external caller wants to initiatea call to the end point inside, it will make a call to the specificIP/port pair on the firewall instead. The firewall will then use thesame technique described above, to change the packet header and thecontent, so that the VoIP traffic can traverse the firewall. Embodimentsof the present invention thus allow multiple calls to multiple endpoints behind the firewall. Embodiments of the present invention thusextend the capabilities of the firewall from a single port managementscheme to a firewall capable of managing multiple incoming VoIP calls byproviding multiple ports on the firewall interfaces. Each of these portsis mapped to an internal endpoint, so that multiple VoIP calls tomultiple endpoints inside the firewall are now completely manageable bythe firewall.

Referring to FIG. 4, the processing steps carried out by a firewall willnow be described for managing an incoming IP packet according to oneembodiment of the present invention. According to the present example,the process begins (step 200) by checking if an incoming packet is aVoIP packet (step 205), if it is not, then regular firewall processes ofthe packet are performed (step 220). If the incoming IP packet is a VoIPpacket, then a table lookup process is carried out to identify an endpoint IP address and the internal port number that matches with the portnumber designated by the incoming VoIP packet (step 210). The firewallthen changes the IP address and the port number of the VoIP requestembedded in the IP packet to be consistent with the end point IP addressand port number as recognized by the internal network (step 215). Thefirewall then carries out further regular firewall processes on the VoIPpacket (step 220) before the firewall processes are ended (step 230).

Example 1 as described below provides a specific implementationaccording to one embodiment of the present invention. The Example isprovided to further illustrate a network protection gateway (NPG) thatapplies an intelligent VoIP-aware network address translation (NAT)solution while enabling comprehensive network protection functions in asingle unit. The intelligent NPG of the example is implemented as anapplication specific integrated circuit (ASIC)-based real-timeanti-virus protection, connection filtering, firewall, VPN, intrusiondetection, and traffic-shaping device. The comprehensive intelligent NPGtakes advantage of an “application-aware” feature of the device toimplement the techniques disclosed, such as “VoIP-aware” NAT services.

EXAMPLE 1

The device of this Example recognizes H.323 messages based on thestandard port 1720-port address and parses the body of H.323 messagesWhen it recognizes specific H.323 messages that carry the RTP/RTCPaddresses, the NPG device creates the IP/Port mapping for the RTPtraffic, which allows proper identification and address mapping of theRTP media stream between the calling and called devices in the privateIP space and call host or IP gateways in the public space. It is assumedthat a person of ordinary skill in the art possesses moderate level ofknowledge of VoIP, RTP, H.323, H.225.0, H.245, VoIP's deployment in anenterprise network, and basic NAT technology.

The Core Intelligence of the NGP Device: H.323 Message Parsing

The processes of H.323 message parsing and translation of a typicalMicrosoft “Netmeeting session” setup is described. A Netmeeting uses theH.323 protocol for signaling and data transmission. VoIP calls throughan IP PBX operate in a slightly different but similar fashion.

FIG. 5A shows the network topology involved in the example Netmeetingsession. In the middle sits a NPG device shown as a “FortiGate unit”provided by CoSine Communications, Inc., which acts as a networkprotection gateway between the external network (“Public Network” as itis called in the diagram) and the internal network, which has multiplelocal hosts (named Internal Host 1 through 3 in the diagram). Forconvenience, the Internal Host 2 is named as “Lisa”. Also sitting on theprivate network protected by the FortiGate NPG is the NetMeeting“Gatekeeper” server.

Introduction to the H.323 Gatekeeper

The Gatekeeper (GK) is used in the context of the H.323 protocol (and isused in other media control protocols as well). The GK is considered the“brains” of an H.323 signaling system. Typically, a GK is required whenmore than one local host needs to receive or initiate VoIP calls orhost/participate in Netmeeting sessions. The Gatekeeper keeps aregistration table where the private IP addresses of the local hosts aremapped to the “Alias” of that particular local host. In a Netmeetingsession, an Alias is used to identify a party involved in a call. In thepresent example, assuming the email addresses of the users of theinternal hosts are used in Netmeeting to uniquely identify theparticipants, the table that the GK keeps will look like the following:

Other User Local Host Private IP User Alias Information 192.168.1.15doug.smith@lebeis.com . . . 192.168.1.10 Lisa.Kelly@lebeis.com . . .192.168.1.27 Joe.han@lebeis.com . . . . . .

Note that an assumption is made that the e-mail addresses of threeusers, i.e., doug.smith@lebeis.com, lisa.Kelly@lebeis.com, andjoe.han@lebeis.com are using the three machines on the local network asillustrated in the above chart. On receiving an H.323 related messagedirected to it by the FortiGate gateway, the Gatekeeper will use theabove mapping table to direct the message to the appropriate local hostbased on the User Alias value, which is used in the Netmeeting sessionas an identifier of a person to call. The table in the Gatekeeper isempty when no Netmeeting client has been started on the local network.Note that if multiple Gatekeepers are deployed across a company's WAN,they synchronize between themselves for registered user information.Gatekeepers communicate with end points (local hosts in this case) usinga protocol called RAS, or Registration, Admission, and Status. RAS is astraightforward protocol used by endpoints to register with a Gatekeeperfor the purposes of call setup with another H.323 endpoint. In ourexample, as soon as a user, let's say, Lisa, starts her Netmeetingclient on her local host 192.168.1.10, her private IP address and herUser Alias (stored in the Netmeeting client) lisa.kelly@lebeis.com willbe entered into the gatekeeper's table.

The following descriptions explain the entire process of Netmeetingsetup using H.225.0, a sub-protocol of the H.323 protocol designed forcall setup and teardown. Eight steps are described in FIG. 5B thatconstitute the initial part of the Netmeeting setup process. An analysisof the eight steps highlights the problems that are involved in VoIP NATtraversal, and shows how the FortiGate content-aware packet and contentstream inspection according to the techniques disclosed herein solvesthe problem to allow VoIP traffic to traverse the bafflers generated bythe NAT process.

In the example, it is assumed that Andy, the external user, is hosting aNetmeeting session. Andy has a public IP address of 64.58.79.231. Andy'semail address is andy.huang@external.com Lisa Kelly will be joining theNetmeeting session from behind the FortiGate gateway.

The Call Model of H.323

The H.323 call model supports many methods for setting up and routingcalls, such as direct point-to-point (no Gatekeeper), point-to-pointwith routing via a Gatekeeper, multi-point, etc. This example examinesthe “Gatekeeper routed” model in the context of a point-to-pointNetmeeting call through H.323.

The call model of H.323 consists of five phases:

-   -   1. Call setup (Phase A)    -   2. Initial communication between endpoints and terminal        capability exchange (Phase B)    -   3. Establishment of audio and/or visual communication between        endpoints (Phase C)    -   4. Request and negotiation of Call Services (Phase D)    -   5. Call termination (Phase E)

In the following descriptions, the initial stage of Phase A and part ofPhase C are described to illustrate the potential problems VoIP callsetup/data transmission currently experience and show how theembodiments of the present invention seek to alleviate the problems.

H.323 Case Study, Phase A: Call Setup

Step 1: User Registration in the Gatekeeper through RAS

Referring to FIG. 5B, the initial stage of the call set-up processeswill now be described in accordance with one embodiment of the presentinvention. As discussed earlier, to join the Netmeeting hosted by AndyHuang, Lisa opens the Netmeeting client. Earlier, she enabled the“Advanced Calling Options/Use a Gatekeeper to Place a Call” in theNetmeeting client, where she entered 192.168.1.2, or the private IPaddress of the Gatekeeper on her local area network through which herNetmeeting packets will be routed as shown in FIG. 5C. The table in thegatekeeper will then add the mapping between Lisa's private IP addressto her alias (lisa.Kelly@lebeis.com) as a new entry. This process iscompleted through UDP protocol and port 1719.

Once Lisa starts the Netmeeting client (which in the background causesher to be registered onto the Gatekeeper), she types in Andy's public IPaddress (64.58.79.231), which is used to find him as shown in FIG. 5D,and clicks on “Call”. What happens in the background is that Lisa'sNetmeeting sends a H.225.0 call setup TCP packet to the Gatekeeper. Notethat Lisa's Netmeeting client is set up in such a way that all the callrelated packets (call setup, call data transmission, call teardown,etc.) will be routed to the Gatekeeper before being relayed to thenetwork gateway connected to the external network. The TCP packet lookslike that shown in FIG. 5E. The source IP address shows Lisa's privateIP and the destination IP shows Andy's public IP address; thedestination port is 1720, the H.225.0 call setup port that must be openon Andy's machine. Note also that in the message body, there isinformation about the Source IP and the Source Port— Andy, as theNetmeeting host will be using the this information in the message bodyto reply to Lisa to try to setup the call. This constitutes the firstmajor VoIP NAT traversal problem that will be described in step 2.Lisa's alias is also embedded in the message body for future use.

Step 2: Call Setup Failure Using a Conventional NAT Gateway

In the present example, the Gatekeeper is pre-configured to have192.168.1.1, or the internal IP address of the FortiGate gateway as itsdefault gateway to the Internet. All packets it receives from theinternal hosts will be relayed to the FortiGate unit (except for theinitial caller registration information).

If the FortiGate of the present example handled NAT like a conventionalfirewall, the FortiGate unit would translate all internal host IPaddresses into a public address (typically the external interface IPaddress of 205.10.10.10, or if an external IP address pool isavailable—into one of the addresses from the pool). The internaladdresses, such as 192.168.1.10, are not routable outside of theinternal network.

A security gateway, such as a conventional firewall that understands andtranslates only the header of the packets, will change the packet asthat shown in FIG. 5F. Note that the source IP and the Source Portnumbers have been changed from their original internal host (Lisa's)into the external IP address of FortiGate (205.10.10.10); similarly, thePort number may or may not be changed (in this case, it's changed from2427 into 10000). Note the Source IP and Source Port in the message bodyare not touched because conventional firewalls don't look beyond packetheaders. The problem arises when Andy's Netmeeting application tries totalk to Lisa to set up the call—remember as mentioned earlier it is theSource IP and Source Port embedded in the message body that will be usedto locate the host at the other end of Andy's Netmeeting call. Andy'sapplication will then try to send a TCP packet back to destinationaddress 192.168.1.10_with destination port=2427. This packet will belost because the address 192.168.1.10 is not routable outside of Lisa'sinternal network. The result—the reply packet sent by Andy will be lostand the Netmeeting call attempt will be aborted. In essence, the VoIPNAT traversal problem arises because the media transmission andsignaling protocols, such as H.323, SIP, MGCP, and MegaCo, makeextensive use of the information embedded in the message body in packetsrather than relying exclusively on the packet header for routing.Conventional firewalls understand and process only the header withnetwork address translation and don't touch the message body.Consequently, the other side of the media session will be using thewrong information to route its reply and communication attempts willfail.

Step 2 Revisited: Call Setup Success Using a Fortigate Gatewayconfigured in accordance with an embodiment of the present invention

In this example, the FortiGate unit's application—aware NAT technologyavoids the problems experienced using a conventional, network-level NATsolution. The FortiGate unit receives the TCP Netmeeting call setuppacket from the Gatekeeper, and by parsing the message, recognizes theH.323 call setup request. As a result, besides the normal networkaddress translation that FortiGate unit performs on every outgoingpacket, it performs a “message body address translation” as well byreplacing the source IP and source port in the message body with anexternally routable IP and port number, as illustrated in FIG. 5G.According to one embodiment, all the above processing is completedwithin the proprietary purpose-built FortiOS™ operating system kerneland therefore latency introduced as a result of the packet parsing isnegligible.

Step 3, 4, 5, and 6: Andy Receives and Responds to the Call SetupRequest

Once the header-level NAT is completed together with the addresstranslation in the message body, the call setup request (TCP packetdestined towards Andy's port 1720) will be sent to the external networkthat FortiGate is connected to and routed to Andy's machine at public IPaddress 64.58.79.231. Andy's machine is listening on port 1720 for callsetup requests. It picks up the setup request from Lisa, removes theheader, and looks into the message body to pick out the Source IP andSource Port from there. It understands that the Lisa can be reached atSource IP address 205.10.10.10 (which is the external interface addressof FortiGate) and at port 10000. It also understands that Lisa is calledon her in Netmeeting by her Alias lisa.Kelly@lebeis.com. It then sends aTCP call setup reply back to Lisa as illustrated in FIG. 5G: The replygets routed through the public network and arrives at the FortiGateexternal interface.

Steps 6-7-8: The FortiGate Unit and Gatekeeper Implement IntelligentH.323 Call Setup

When the call setup reply arrives at the FortiGate unit's externalinterface, several things happen:

-   -   1. The FortiGate unit parses all incoming packets and recognizes        the H.225.0 call setup reply packet by looking at the header of        the TCP packet—all Source Port=1720 packets are by design        H.225.0 call setup packets.    -   2. The FortiGate implements “Port Forwarding,”—in this case it        has been configured to route all packets with a Source port        =1720 to the Gatekeeper.    -   3. The Gatekeeper, on receiving the packet, understands that the        packet is for call setup and is a reply from the host of the        Netmeeting session. The Gatekeeper parses the message and        understands that the call participant's alias is        lisa.kelly@lebeis.com. It then looks it up in its mapping table        and finds the private IP for Lisa at 192.168.1.10. The reply        packet is then relayed onto Lisa's machine.    -   4. Once the call setup reply from Andy arrives at Lisa's machine        and is appropriately processed, the initial H.225.0 call setup        is completed.        The Processes for Andy to Call in as A Participant and Lisa to        Host a Netmeeting:

Up until now, it has been assumed in the example that Lisa calls out tojoin Andy's Netmeeting. What if Lisa hosts a Netmeeting and Andy callsin to join? In this situation, all that needs to be done according toone embodiment is to turn on the H.323 support in the FortiGategateway—the same as when it is desired to enable Lisa to call out. Noport will have to be permanently opened in the firewall to enable Andy'srequest to get through.

When Andy initiates a Call setup request to join Lisa's meeting therequest TCP packet will arrive at the FortiGate gateway with adestination port of 1720. The FortiGate unit will use port addressforwarding to redirect the packet to the Gatekeeper, which will in turnforward it onto Lisa's host (based on Lisa's alias oflisa.kelly@lebeis.com) for further processing. Lisa's reply will begoing through similar address and port translation as described above.This way security is not jeopardized while incoming calls are allowed.

H.323 Case Study, Phase C: H.323 Establishment of MediaCommunication—H.245 Logical Channel Setup

Once the initial call setup is completed, both sides can exchangeinformation to set up the Master/Slave status in the call and also telleach other what kind of capabilities (video, audio, etc.) are availableon both sides. The next stage would be to set up the logical channel forRTP, or Real Time Protocol, which carries the voice and/or videochannels. The most important part in logical channel setup is the portaddress exchange so that both sides know which port to direct the mediatraffic to in media transmission. As before, a step-by-step analysishighlights the relevant FortiGate operations that facilitate the portsetup process.

Step 1, 2, and 3: Lisa Initiates a Logical Channel Setup Message

RTP is the protocol used in H.323 for media data transmission, includingboth video and audio. Logical channel setup focuses on exchanging UDPport information to the parties involved in the call to set up the portfor media data exchange. This process is accomplished through the H.245protocol, a sub-protocol in H.323. In this example, Lisa sends a logicalchannel setup UDP packet to Andy. The packet is illustrated in FIG. 5I.Note that the message body carries the source IP address as well as theport address to be used for RTP data transmission. Similar to Phase A inCall Setup, without appropriate replacement of the IP and Port in themessage body, Andy won't know the appropriate port number for Lisa andtherefore the media data transmission piece won't go through. This wouldbe the case if a conventional NAT/firewall were used, and thus the callwould fail.

The FortiGate unit configured in accordance with an embodiment of thepresent invention inspects both the header and message body of packets,and through its proprietary masquerading function, it will generate anIP address/Port pair that will be used to replace the Source IP/SourcePort in the message body as well as in the header. The mapping will beentered into its mapping table as illustrated in FIG. 5J. The UDP packetafter the translation is illustrated in FIG. 5K. This new packetcarrying translated address and port information will then be sent toAndy. Note that the ports that opened for the media transmission sessionwill be opened only for the duration of the session and will bedynamically closed immediately after the session is over. Thiseliminates the severe security vulnerabilities that are introduced whenpre-defined ports are left open permanently, as is often the case usingconventional NAT firewalls.

Step 4, 5, 6: Andy's Netmeeting Client Responds to Lisa's LogicalChannel Setup Request

On receiving Lisa's logical channel setup request, Andy's NetmeetingClient will respond by sending a reply carrying its own port address,and will send the packet to address 205.10.10.10 and port 10000 asindicated in Lisa's message body. The response will travel across thepublic network and arrive at the FortiGate gateway.

Step 7, 8: Andy's Response Intelligently Routed to Lisa

Once the response arrives at FortiGate, it will use the mapping table totranslate it into the Private IP as well as the private port addresscorresponding to Lisa's machine and Netmeeting application. Similar toPhase A Call setup, using port address forwarding the logical channelsetup response from Andy will then be forwarded to the Gatekeeper, whichwill relay (without further processing) the response to the correct porton Lisa's machine, thus completing the logical channel setup process andenabling a secure VoIP session.

According to Example 1, a firewall is disclosed that is an applicationaware firewall provided for detecting outgoing VoIP packets. In oneembodiment, the firewall is an application aware firewall provided fordetecting outgoing VoIP packets based on a standard port address. Inanother embodiment, the firewall further includes an external VoIPinterface for mapping an e-mail address included in an incoming VoIPmessage to an internal port number in the internal network. In anotherembodiment, the firewall further includes an external VoIP interface forcoordinating with the VoIP processing means for conducting a networkmeeting between an external network user and at least two internalnetwork users. In another embodiment, the firewall further includes anexternal VoIP interface for coordinating with the VoIP processing meansfor conducting a network meeting between an internal network user and atleast two external network users.

Embodiments of the present invention further provide a networkprotection gateway device that has an application awareness means forrecognizing a VoIP message and a VoIP processing means for parsing andprocessing the VoIP message for enabling a protected bi-direction VoIPcommunication.

In one embodiment, the NPG further includes an application specificintegrated circuit (ASIC) for implementing the network protectiongateway therein.

Embodiments of the present invention further provide a method fortransmitting a VoIP packet from an internal network through a firewallto an external network comprising a step of detecting an outgoing VoIPpacket sent from the internal network for changing data in a header ofthe VoIP packet and also changing data contents in the VoIP packetcorresponding to data changed in the header to enable a bi-directionalVoIP communication. In accordance with one embodiment, the step ofchanging the data in the header of the VoIP packet comprises a step ofchanging a source IP address and a port number in the header of the VoIPpacket and the step of changing the data contents in the VoIP packetfurther comprises a step of changing the data contents in the VoIPpacket corresponding to the source IP address and the port numberchanged in the header to enable a bi-directional VoIP communication.According to one embodiment, the method further includes a step ofproviding a plurality of VoIP ports to an external VoIP interface forreceiving multiple incoming VoIP packets each designated with one of theVoIP ports; and identifying an internal address in the internal networkcorresponding to the VoIP port designated in each of the incoming VoIPpackets for directing each of the incoming VoIP packets to the internaladdress identified. In one embodiment, the method further includes astep of mapping an e-mail address included in an incoming VoIP messageto an internal port number in the internal network. In anotherembodiment, the method further includes a step of conducting a networkmeeting between an external network user and at least two internalnetwork users. In another embodiment, the method further includes a stepof conducting a network meeting between an internal network user and atleast two external network users.

Therefore, according to embodiments of the present invention NetworkProtection Gateways (NPGs) are specifically designed to provide theapplication-level intelligence and ASIC—accelerated performance requiredfor secure Internet telephony and mixed voice/data applications. In oneembodiment, NPG supports secure VoIP services for any size company— fromSOHO users through large enterprises and service providers—and enablesany organization to take full advantage of the benefits of convergedvoice/data applications.

Although the present invention has been described in terms of variousspecific embodiments, it is to be understood that such disclosure is notto be interpreted as limiting. Various alterations and modificationswill no doubt become apparent to those skilled in the art after readingthe above disclosure. Accordingly, it is intended that the appendedclaims be interpreted as covering all alterations and modifications asfall within the true spirit and scope of the invention.

1. A method comprising: a firewall, interposed between an internalnetwork and an external network, providing network-layer protectionagainst unauthorized access by hosts associated with the externalnetwork to a plurality of internal hosts associated with the internalnetwork by performing network address translation (NAT) processing ofInternet Protocol (IP) addresses associated with the plurality ofinternal hosts; the firewall providing application-layer protection fromthe external network on behalf of the plurality of internal hosts andsupporting VoIP services without compromising internal network securityby actively processing signaling protocols associated with Voice over IP(VoIP) sessions, including distinguishing among VoIP packets andnon-VoIP packets, understanding and parsing the VoIP packets at theapplication layer, and performing content-aware NAT by changing data inheaders of the VoIP packets and also changing data contents in the VoIPpackets corresponding to data changed in the headers to enablebi-directional VoIP communications among one or more of the plurality ofinternal hosts and one or more of the hosts associated with the externalnetwork; providing a plurality of VoIP ports to an external VoIPinterface of the firewall; receiving by the external VoIP interfaceincoming VoIP packets each having associated therewith a user alias andan indication regarding one of the plurality of VoIP ports; causing eachof said received multiple incoming VoIP packets to be directed to anappropriate internal host of the plurality of internal hosts byperforming by the firewall port address forwarding based on the portindication to an H.323 gatekeeper within the internal network thatmaintains a mapping of user aliases to private addresses of theplurality of internal hosts; wherein the user alias comprises an emailaddress of a user associated with one of the plurality of internalhosts; and wherein the firewall comprises an intelligent networkprotocol gateway device.
 2. The method of claim 1, wherein said changingdata in headers of the VoIP packets further comprises changing a sourceIP address and a port number in the headers of the VoIP packets.
 3. Themethod of claim 1, wherein said distinguishing among VoIP packets andnon-VoIP packets is based on a standard port address.
 4. The method ofclaim 1, further comprising conducting through the external VoIPinterface a network meeting between an external network user and atleast two internal network users.
 5. The method of claim 1, furthercomprising conducting through the external VoIP interface a networkmeeting between an internal network user and at least two externalnetwork users.
 6. The method of claim 1, further comprising implementingsaid firewall as an application specific integrated circuit (ASIC). 7.An intelligent network protection gateway device comprising: a networkaddress translation (NAT) processing means, configured to be interposedbetween an internal network and an external network, for providingnetwork-layer protection against unauthorized access by hosts associatedwith the external network to a plurality of internal hosts associatedwith the internal network by performing translation of Internet Protocol(IP) addresses associated with the plurality of internal hosts; anapplication-layer protection means, for protecting the plurality ofinternal host from the external network and for supporting VoIP serviceswithout compromising internal network security by actively processingsignaling protocols associated with Voice over IP (VoIP) sessions,including distinguishing among VoIP packets and non-VoIP packets,understanding and parsing the VoIP packets at the application layer, andchanging data in headers of the VoIP packets and also changing datacontents in the VoIP packets corresponding to data changed in theheaders to enable bi-directional VoIP communications among one or moreof the plurality of internal hosts and one or more of the hostsassociated with the external network; an external VoIP interfaceincluding a plurality of VoIP ports configured to receive incoming VoIPpackets each having contained therein an a user alias and an indicationregarding one of the plurality of VoIP ports; wherein said external VoIPinterface further comprises a means for directing the incoming VoIPpackets to an appropriate internal host of the plurality of internalhosts by performing port address forwarding based on the port indicationto an H.323 gatekeeper within the internal network that maintains amapping of user aliases to private addresses of the plurality ofinternal hosts; wherein one or more of said NAT processing means andsaid application-layer protection means includes (i) logic implementedwithin an application specific integrated circuit (ASIC) of theintelligent network protection gateway device or (ii) a program storagedevice readable by one or more processors of the intelligent networkprotection gateway device, tangibly embodying a program of instructionsexecutable by the one or more processors; wherein the user aliascomprises an email address of a user associated with one of theplurality of internal hosts; and wherein the mapping maps an e-mailaddress included in an incoming VoIP message to an internal port numberin said internal network.
 8. The intelligent network protection gatewaydevice of claim 7, wherein said distinguishing among VoIP packets andnon-VoIP packets is based on a standard port address.
 9. The intelligentnetwork protection gateway device of claim 7, wherein the external VoIPinterface facilitates network meetings among an external network userand at least two internal network users.
 10. The intelligent networkprotection gateway device of claim 7, wherein the external VoIPinterface facilitates network meetings among an internal network userand at least two external network users.